[57978] Mobile: Scrolling quickly to the top or bottom will not show top or bottom on the first try #16880
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
…ditional scrollbar when on mobile devices the adress bar is shown. The adress bar is part of the 100vh but not of 100dvh.
mrmir
deleted the
bug/57978-mobile-scrolling-quickly-to-the-top-or-bottom-will-not-show-top-or-bottom-on-the-first-try
branch
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Ticket
https://community.openproject.org/projects/openproject/work_packages/57978/activity
What are you trying to accomplish?
On mobile browsers there were often two scrollbars causing parts of the application to be hidden.
What approach did you choose and why?
The height of the content was previously calculated with
100vh. On mobile however, the browser adress bar counts into that. Therefore all modern browers supportdvhwhich ignores the adress bar.This only happened now, because we had special mobile scrolling rules which I removed recently.